Vehicle electronic logging device (ELD) hour-of-service (HoS) audit and correction guidance system and method of operating thereof

ABSTRACT

A vehicle electronic logging device (ELD) hour-of-service (HoS) audit and correction guidance system provides preemptive pre-violation and violation alerts and interactive vehicle log entry correction guidance for commercial vehicle operations regulatory compliance. The vehicle ELD HoS audit and correction guidance system incorporates in-vehicle sensor data output values that are machine-interpreted by a vehicle OBD device, a driver&#39;s on-duty or off-duty confirmation entries, and other driver log adjustments to analyze an electronically-generated vehicle log. Subsequently, the system determines whether some log entries are anomalous and indicative of driver log entry or adjustment errors, which may result in commercial vehicle regulatory violation if left uncorrected. The vehicle ELD HoS audit and correction guidance system then prompts and assists a driver to correct anomalous log entries to prevent regulatory violations via interactive driver auditing-mode interfaces, multimedia alerts, sirens, and multi-language voice guidance.

BACKGROUND OF THE INVENTION

The present invention generally relates to one or more electronicsystems for commercial vehicle operations recordkeeping, analysis, andcommunications. More specifically, various embodiments of the presentinvention relate to machine-initiated guidance of vehicle electroniclogging device hour-of-service audit and correction interfaces forregulatory compliance of commercial vehicles and commercial drivers.Furthermore, various embodiments of the present invention also relate tomachine-generated intelligent voice guidance components forhour-of-service audit and correction for regulatory complianceassociated with commercial vehicles and drivers.

Commercial vehicle operations and commercial vehicle drivers areincreasingly regulated and legally mandated by state, federal, national,and/or municipal governments to record and submit proof of commercialvehicle operating history, driver resting period compliance, vehiclecondition inspections, and vehicle maintenance compliance in an effortto enhance public roads safety. For example, in the United States, acommercial vehicle driver is increasingly obligated by variousregulatory compliance measures to record and update his or her vehicleoperating status and legally-mandated resting activities between vehicleoperations. Failure to meet such regulatory requirements in vehicleoperating logs may result in significant penalties imposed on commercialvehicle drivers and their employers.

In one example of regulatory requirements on a commercial vehicledriver, the driver is required to take a mandatory thirty-minute breakafter eight hours of consecutive driving or active on-duty tasksassociated with the commercial vehicle (i.e. “30-minute required breakper consecutive 8-hour drive”). The commercial vehicle driver may alsobe required to abide by other mandatory rest requirements, such as aconsecutive rest period of thirty-four hours for every non-consecutivesixty hours of active on-duty driving per week (i.e. “60-hour cyclelimit”), or a consecutive rest period of ten hours, including eighthours of sleep, for every non-consecutive eleven hours of active on-dutydriving (i.e. “11-hour driving limit”). A regulatory violationintentionally or inadvertently caused by a commercial vehicle driver mayresult in stiff penalties or fines to the commercial vehicle driver anda related vehicle fleet operator.

In the past, the regulatory compliance for mandatory driver rest periodsand vehicle maintenance for commercial vehicle operations was primarilysatisfied by recording driver logs on paper (i.e. in form of “vehicledriver log” documents). In recent years, electronic driveractivity-logging devices have further assisted commercial vehicledrivers to enter or verify their active driving or resting statuses inelectronically-generated driver activity logs. Theelectronically-generated driver activity logs are typically designed tobe periodically reviewed by regulatory authorities and/or fleetoperation managers to improve traffic safety and to provide legalcompliance. In many cases, the electronically-generated driver activitylogs are configured to be tamperproof or “locked” from furtheradjustments by relevant commercial vehicle driver(s) after a set amountof time (e.g. 12 hours, 24 hours, etc.) has elapsed from the actual timeof data recording. The time elapse-triggered “locking” of theelectronically-generated driver activity logs is intended to preservethe integrity of the driver activity logs for more robust regulatorycompliance associated with mandatory commercial driver restingrequirements.

Unfortunately, the “locking” of the driver activity logs may also bringan unintended side effect of preventing honest mistakes or mis-entriesfrom legitimate amendments or corrections in a reasonable timeframe.Furthermore, conventional paper-based or electronically-generated driveractivity logs do not provide intuitive methods or guidance to enable acommercial vehicle driver or a vehicle operations manager to audit orcorrect an inadvertent mistake in the driver activity log entries beforethe time elapse-triggered “locking” of the driver activity log isengaged.

Therefore, it may be desirable to devise a novel electronic system thatproactively identifies potentially-erroneous or incorrect driveractivity log entries in real time and provides an intuitive log entryaudit and correction interface and guidance to commercial vehicledrivers and commercial vehicle operation managers. Furthermore, it mayalso be desirable to devise a dynamically-adaptable intelligent voiceassistant incorporated into the novel electronic system to provideproactive voice guidance through log entry audit and correction modesand user interfaces for accommodating intuitive methods of log entrycorrections and amendments. In addition, it may also be desirable todevise a novel electronic system that determines and alertschronically-inaccurate and “problematic” commercial vehicle driversand/or commercial vehicles that cause repeated and inaccurate driver logentries in order to minimize regulatory penalties and optimizecommercial vehicle operations.

SUMMARY

Summary and Abstract summarize some aspects of the present invention.Simplifications or omissions may have been made to avoid obscuring thepurpose of the Summary or the Abstract. These simplifications oromissions are not intended to limit the scope of the present invention.

In one embodiment of the invention, a commercial fleet-level electroniclogging device (ELD) log audit and correction guidance system isdisclosed. This system comprises: a vehicle on-board diagnostics (OBD)device connected to an engine control unit (ECU) or a vehicular controlchip in a vehicle to record, diagnose, and generate an engine on or offstatus, vehicle speed data, acceleration and deceleration data, ambientair temperature data, and OBD fault codes as a raw OBD data stream; avehicle electronic logging device (ELD) connected to the vehicle OBDdevice, wherein the vehicle ELD is configured to generate adriver-specific ELD log that contains a currently logged-in driver'son-duty, off-duty, and resting activities associated with the vehicle;an ELD and OBD data transceiver connected to the vehicle ELD, whereinthe ELD and OBD data transceiver is configured to transmit ELD and OBDdata to components of the commercial fleet-level ELD log audit andcorrection guidance system that are located outside the vehicle; acommercial vehicle-specific ELD log audit and correction guidanceapplication executed in a first portable electronic device for thecurrently logged-in driver, wherein the commercial vehicle-specific ELDlog audit and correction guidance application detects and identifies apotential error in the driver-specific ELD log that contains thecurrently logged-in driver's on-duty, off-duty, and resting activitiesassociated with the vehicle, and wherein the commercial vehicle-specificELD log audit and correction guidance application generates a driverauditing-mode interface and an interactive voice guidance to prompt thecurrently logged-in driver to correct the potential error to avoid aregulatory violation; a commercial fleet-level multiple vehicle ELD logand database management system that analyzes, stores, and categorizes aplurality of driver-specific ELD logs for a plurality of drivers andvehicles in a commercial fleet operation; and a data communicationnetwork configured to provide a wireless data information transfer amongthe vehicle ELD, the ELD and OBD data transceiver, the first portableelectronic device, and the commercial fleet-level multiple vehicle ELDlog and database management system.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a system block diagram of a commercial fleet-levelelectronic logging device (ELD) hour-of-service (HoS) audit andcorrection guidance system, in accordance with an embodiment of theinvention.

FIG. 2 shows a driver auditing-mode screenshot from an ELD HoS audit andcorrection guidance system, in accordance with an embodiment of theinvention.

FIG. 3 shows another screenshot of a driver auditing-mode from an ELDHoS audit and correction guidance system, in accordance with anembodiment of the invention.

FIG. 4 shows a driver status log edit screenshot from an ELD HoS auditand correction guidance system, in accordance with an embodiment of theinvention.

FIG. 5 shows a driver auditing-mode screenshot after driver-initiatedcorrections from an ELD HoS audit and correction guidance system, inaccordance with an embodiment of the invention.

FIG. 6 shows a vehicle and driver selection interface screenshot from anELD HoS audit and correction guidance system, in accordance with anembodiment of the invention.

FIG. 7 shows a commercial driver electronic logging current status menuscreenshot from an ELD HoS audit and correction guidance system, inaccordance with an embodiment of the invention.

FIG. 8 shows a system block diagram example for a vehicle electroniclogging device (ELD), in accordance with an embodiment of the invention.

FIG. 9 shows an ELD log audit and correction module in an ELD HoS auditand correction guidance system, in accordance with an embodiment of theinvention.

FIG. 10 shows an example of a portable electronic device incorporating acommercial vehicle-specific ELD HoS audit and correction guidanceapplication, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. Like elements in the variousfigures are denoted by like reference numerals for consistency.

In the following detailed description of embodiments of the invention,numerous specific details are set forth in order to provide a morethorough understanding of the invention. However, it will be apparent toone of ordinary skill in the art that the invention may be practicedwithout these specific details. In other instances, well-known featureshave not been described in detail to avoid unnecessarily complicatingthe description.

The detailed description is presented largely in terms of description ofshapes, configurations, and/or other symbolic representations thatdirectly or indirectly resemble one or more novel vehicle electroniclogging device (ELD) hour-of-service (HoS) audit and correction guidancesystems with dynamic voice assistance that provide intuitive andproactive guidance for auditing and amending inadvertent commercialdriver log errors. These descriptions and representations are the meansused by those experienced or skilled in the art to most effectivelyconvey the substance of their work to others skilled in the art.

Reference herein to “one embodiment” or “an embodiment” means that aparticular feature, structure, or characteristic described in connectionwith the embodiment can be included in at least one embodiment of theinvention. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment. Furthermore, separate or alternative embodiments arenot necessarily mutually exclusive of other embodiments. Moreover, theorder of blocks in process flowcharts or diagrams representing one ormore embodiments of the invention does not inherently indicate anyparticular order nor imply any limitations in the invention.

For the purpose of describing the invention, a term referred herein as a“vehicle on-board diagnostics (OBD) device” is defined as an electronicdevice installed in a vehicle to collect and/or analyze a variety ofvehicle-related data. In one example, the vehicle OBD device outputsmany data parameters in real-time, such as vehicle diagnosticinformation (e.g. engine temperature, oil level, OBD codes, and etc.),fuel consumption-related information, vehicle speed information, vehicleacceleration and deceleration information (i.e. measured in g-force orin SI units), ambient air temperature information, enginerotation-per-minute (RPM) information, vehicle location information, andother vehicle-related data. The OBD device is typically connected to anengine control unit (ECU) and a plurality of in-vehicle control orsensor components, such as an accelerometer, a speedometer, athermostat, a barometer, an emissions control unit, a vehicleelectronics control unit, and any other in-vehicle electronicscomponents to check and diagnose the current condition of each connectedvehicle component.

Output data parameters from the vehicle OBD device may be utilized todetermine a driver's driving activity status and regulatory complianceon the driver's activities as mandated by municipal, state, or federalauthorities. The output data parameters from the vehicle OBD can alsodetermine a vehicle malfunction status or a vehicle repair need. Forexample, if the vehicle has a nonzero speed for a certain amount of timewhile its engine is running, an associated commercial driver's drivingactivity status may be determined by a vehicle electronic logging deviceas being engaged in an “on-duty” status. In another example, if thevehicle has a zero speed for a certain amount of time while its engineis idling, the associated commercial driver's driving activity statusmay be determined by the vehicle electronic logging device as stillbeing engaged in an “on-duty” status. On the other hand, if thevehicle's engine itself is turned off for a certain amount of time, theassociated commercial driver's driving activity status may be determinedby the vehicle electronic logging device as being “off-duty,” inactive,and/or restful from work. Furthermore, an OBD malfunction code or anabnormal data reading as part of the output data parameters from thevehicle OBD device may indicate or identify the source and the state ofthe vehicle malfunction.

These data parameters may also be correlated to timestamps generated byan electronic clock associated with the vehicle OBD device. In oneembodiment of the invention, the data parameters may be generated by thevehicle OBD device in a region-specific, maker-specific, and/ormodel-specific format, which requires interpretation and conversion to acompatible output format decodable by a vehicle electronic loggingdevice, a mobile application executed on a portable electronic device,and/or a remotely-located commercial fleet operation vehicle electroniclogging database and management system.

Furthermore, for the purpose of describing the invention, a termreferred herein as a “vehicle electronic logging device,” or an “ELD,”is defined as a specialized driver activity log-generating electronicdevice connected to a vehicle OBD device. This specialized driveractivity log-generating electronic device analyzes real-time OBD outputdata parameters to objectively derive or confirm an ongoing driveractivity and/or vehicle repair needs in a commercial vehicle. Forexample, a vehicle ELD can measure and objectively confirm a commercialvehicle driver's on-duty driving by tracking a nonzero vehicle speeddata parameter and an engine “on” status signal from the vehicle OBDdevice, until the commercial vehicle driver stops and turns off theengine.

Similarly, the vehicle ELD can objectively measure and confirm thecommercial vehicle driver's off-duty resting period with a system clockand a duration of the engine “off” status signal. Machine andsensor-based determination of driving activity statuses from ELD and OBDdevices can be utilized even further to create a commercial vehiclehour-of-service audit and correction guidance system that preemptivelyalerts and guides a related commercial vehicle driver and/or acommercial fleet manager to encourage and accommodate a proactivecorrection of commercial drivers' electronic log entries to avoidunnecessary regulatory violations and to preserve log accuracy andregulatory compliance for commercial vehicle driving activities.

Moreover, the vehicle ELD may be configured to monitor, track, andrecord vehicle malfunction codes from the OBD device and incorporatethem automatically in a driver vehicle inspection report, which may beinitiated, updated, or rectified by a commercial vehicle driver and/or adesignated auto mechanic In addition, regulatory compliance related to arequired duration of the commercial vehicle driver's rest can also betracked and alerted to appropriate authorities (e.g. local, national,and/or federal traffic safety enforcement agencies, fleet managers,etc.) by the vehicle ELD and/or an ELD log audit and correction guidancesystem connected to an in-vehicle data transceiver unit, which furthercommunicates with a remotely-located monitoring station.

In a preferred embodiment of the invention, the vehicle ELD and the ELDlog audit and correction guidance system are also configured to acceptthe commercial vehicle driver's manual data entries and corrections,which are then automatically compared against and/or merged withmachine-determined driver's activity log information derived from thevehicle OBD device to complete synthesis of a new or amendedelectronically-generated driver activity log that incorporates bothobjective (i.e. machine-determined) and subjective (i.e. driver-entered)information for enhanced details and accuracy.

Furthermore, for the purpose of describing the invention, a termreferred herein as “hour of service,” or “HoS” is defined as areal-time, hourly, and/or minutely-managed and monitored commercialdriving activity parameters and logs for commercial vehicle regulatorycompliance required by state, municipal, and/or federal governmentagencies. For example, an electronic logging device (ELD)hour-of-service (HoS) audit and correction guidance system is avehicle-installed ELD that additionally incorporates preemptiveregulatory violation (i.e. “pre-violation”) alert and log amendmentcapabilities to enable early-stage correction (i.e. within minutes orhours of a potential pre-violation log element creation) of potentiallyerroneous commercial driving activity parameters that may have been aresult of a driver's carelessness or machine-generated entry errors.

Moreover, for the purpose of describing the invention, a term referredherein as a “portable electronic device” is defined as a smart phone, atablet computer, a notebook computer, a special-purpose proprietary ELDdata controller device, or another transportable electronic device thatcan execute a vehicle ELD HoS audit and correction guidance and/ormanagement application for a commercial vehicle driver or a vehiclefleet operator.

Furthermore, for the purpose of describing the invention, a termreferred herein as a “remote monitoring station unit” is defined as avehicle fleet monitoring location for one or more commercial vehicles inoperation. Examples of remote monitoring station units include, but arenot limited to, a commercial vehicle operation control center, aregulatory traffic safety enforcement agency, a vehicle monitoringservice center, and a fleet vehicle employer's information technology(IT) control center. Typically, the remote monitoring station unit isconfigured to execute and operate a commercial fleet-level multiplevehicle ELD log and database management system as well as a commercialfleet-level multiple vehicle ELD HoS audit and correction managementapplication in a computer server, a portable electronic device, oranother computerized device.

In addition, for the purpose of describing the invention, a termreferred herein as “computer server” is defined as a physical computersystem, another hardware device, a software module executed in anelectronic device, or a combination thereof. Furthermore, in oneembodiment of the invention, a computer server is connected to one ormore data networks, such as a local area network (LAN), a wide areanetwork (WAN), a cellular network, and the Internet. Moreover, acomputer server can be utilized by a vehicle monitoring personnel forgathering and analyzing electronically-generated commercial vehicledriver logs that are stored, updated, and modified by a commercialfleet-level multiple vehicle ELD log and database management system.

One aspect of an embodiment of the present invention is providing anovel electronic system for commercial driver electronic logging rulecompliance and ELD log entry correction guidance to reduce or preventregulatory violations at an early stage of data abnormality discoveries.

Another aspect of an embodiment of the present invention is providing anovel electronic system, such as an ELD hour-of-service audit andcorrection guidance system, that proactively identifiespotentially-erroneous or incorrect driver activity log entries in realtime and creates an intuitive log entry audit and correction interfaceand guidance to commercial vehicle drivers and commercial vehicleoperation managers.

Furthermore, another aspect of an embodiment of the present invention isproviding a dynamically-adaptable intelligent voice assistantincorporated into the novel electronic system to enable proactive voiceguidance through log entry audit and correction modes and userinterfaces for accommodating intuitive methods of log entry correctionsand amendments.

Yet another aspect of an embodiment of the present invention isproviding a novel electronic system that determines and monitorschronically-inaccurate and “problematic” commercial vehicle driversand/or commercial vehicles that cause repeated and inaccurate driver logentries to minimize regulatory penalties and optimize commercial vehicleoperations.

FIG. 1 shows a system block diagram (100) of a commercial fleet-levelelectronic logging device (ELD) hour-of-service (HoS) audit andcorrection guidance system, in accordance with an embodiment of theinvention. In a preferred embodiment of the invention, the commercialfleet-level ELD HoS audit and correction guidance system comprises anautomotive vehicle, a vehicle on-board diagnostics (OBD) device (119)installed in the automotive vehicle, in-vehicle sensors and an enginecontrol unit (117) connected to the OBD device (119), a vehicleelectronic logging device (ELD) (121), an ELD and OBD data transceiverunit (123), a portable electronic device (101) for a commercial vehicledriver, a commercial vehicle-specific ELD HoS audit and correctionguidance application (103) executed on the portable electronic device(101) for the commercial vehicle driver, a portable or stationaryelectronic device (111) for a vehicle monitoring station operated by acommercial vehicle operations quality controller, a commercialfleet-level multiple vehicle ELD HoS audit and correction managementapplication (113) executed on the portable or stationary electronicdevice (111), a commercial fleet-level multiple vehicle ELD log anddatabase management system (105) executed on a cloud network-connectedcomputer server, and a wired and/or wireless data network (125).Furthermore, the commercial fleet-level ELD HoS audit and correctionguidance system may optionally also include an in-vehicle display (107)connected to the vehicle ELD (121) and an in-vehicle ELD HoS audit andcorrection guidance application (109) executed by the vehicle ELD (121)or by another in-vehicle electronic device per automotive vehicle.

Moreover, as shown in the system block diagram (100) in FIG. 1, thein-vehicle sensors and the ECU (117), the vehicle OBD device (119), thevehicle ELD (121), and the ELD and OBD data transceiver unit (123) aretypically incorporated physically in the automotive vehicle asvehicle-side system components (115) of the commercial fleet-level ELDHoS audit and correction guidance system. In the preferred embodiment ofthe invention, the automotive vehicle is a truck, a van, a bus, oranother commercial operation-registered vehicle, which is typicallyutilized for commercial transport of freight and/or passengers thatinvolve state, federal, municipal, and/or corporate regulations toensure appropriate levels of commercial drivers' mandatory restingperiods between vehicle operations and vehicle maintenance for publicsafety. The electronic commercial driving activity logs and maintenancerecordkeeping requirements are typically based on mileage, calendardays, and/or hours of service for each commercial driver. In anotherembodiment of the invention, the automotive vehicle may be a privatevehicle (i.e. not registered as a commercially-operated vehicle), whichis shared among a plurality of drivers via car ride-sharing services orpassenger transport services.

Furthermore, the vehicle OBD device (119) is a specialized electronicdevice installed in the automotive vehicle to collect and/or analyze avariety of vehicle-related data, including engine on/off status, enginetemperature, OBD fault codes, speed, acceleration, ambient airtemperature, ambient air pressure, engine rotation-per-minute (RPM),vehicle location, and other vehicle-related output parameters generatedby an engine control unit (ECU), a transmission control module (TCM), anaccelerometer, a barometer, a fuel pressure sensor, other in-vehiclesensors (e.g. 117), or other electronic components connected to thevehicle OBD device (119). In the preferred embodiment of the inventionas shown in FIG. 1, output data parameters from the vehicle OBD device(119) are utilized to formulate at least part of a commercial vehicleelectronic driver log that contains a commercial vehicle driver'son-duty/off-duty status, the commercial vehicle driver's restingactivity information, vehicle engine on/off time, driving distanceinformation for a particular on-duty timeframe, and other drivingactivity or status information generated from machines and/or entered bythe commercial vehicle driver. The commercial vehicle electronic driverlog or a driver vehicle inspection report (DVIR) may additionallyindicate that the automotive vehicle requires repairs or maintenancework based on OBD fault codes or other data parameters generated fromthe vehicle OBD device (119). The vehicle OBD device (119) may also beutilized to determine a driver's driving activity status via the vehicleelectronic logging device (ELD) (121), which requires each time-sharedcommercial vehicle driver of the same automotive vehicle to log in orlog off electronically to indicate time periods of specific driveractivity.

Continuing with the embodiment of the invention as shown in FIG. 1, anyOBD fault codes or data parameters from the vehicle OBD device (119)that are related to engine on/off statuses and driving activities becomepart of a particular driver's commercial vehicle electronic driver logautomatically even without human intervention, and are further analyzedand stored by the vehicle ELD (121) and the commercial fleet-levelmultiple vehicle ELD log and database management system (105).Furthermore, a commercial vehicle driver is also typically required toprovide at least some manual information entries into the vehicle ELD(121) via the in-vehicle display (107), the portable electronic device(101), or another data entry-capable electronic interfaces before andafter each commercial driving activity to confirm a driver identity andupdate a current on-duty or off-duty status with the vehicle ELD (121).Commercial vehicle electronic driver logs, OBD codes, and any in-vehiclesensor-originating data parameters that are specific to the automotivevehicle can be remotely transmitted to and further processed by thecommercial fleet-level multiple vehicle ELD log and database managementsystem (105) via the ELD and OBD data transceiver unit (123) and thewired and/or wireless data network (125).

In the preferred embodiment of the invention, the commercial fleet-levelmultiple vehicle ELD log and database management system (105), thein-vehicle ELD HoS audit and correction guidance application (109),and/or the commercial vehicle-specific ELD HoS audit and correctionguidance application (103) may determine that a recent commercialvehicle electronic driver log generated in the last hour, in the lasteight hours, in the last twenty-four hours, or in another recentrecording timeframe may contain unusual or anomalous driver logparameters that are likely to result in commercial vehicle activityregulatory violations, if left uncorrected within a certain time limit.For example, a commercial vehicle driver may simply forget to log out ofa currently-active commercial vehicle electronic driver log managed bythe vehicle ELD (121) after a workday and not return to the vehicleuntil the next morning, which in turn keeps the “on-duty” status activeerroneously throughout the night. Because the currently-activecommercial vehicle electronic driver log has not accurately recorded anend of the commercial vehicle driver's “on-duty” status in thisparticular instance, a federal, state, or municipal regulatory violationmay be triggered after a few days for not taking sufficient rest periodsbetween on-duty driving activities, unless the commercial vehicle driveror an operations manager proactively amends the erroneous information inthe recent commercial vehicle electronic driver log.

As shown in the system block diagram (100) in FIG. 1, the commercialfleet-level multiple vehicle ELD log and database management system(105), the in-vehicle ELD HoS audit and correction guidance application(109), and/or the commercial vehicle-specific ELD HoS audit andcorrection guidance application (103) are configured to detect andidentify such unusual or anomalous driver log parameters that are likelyto result in commercial vehicle activity regulatory violations, if leftuncorrected within a certain time limit Once such unusual or anomalousdriver log parameters are detected and identified, the in-vehicle ELDHoS audit and correction guidance application (109) and/or thecommercial vehicle-specific ELD HoS audit and correction guidanceapplication (103) are configured to provide driver auditing and logentry edit modes in a graphical user interface generated by thein-vehicle display (107) connected to the vehicle ELD (121) or by theportable electronic device (101) for the commercial vehicle driver. Thein-vehicle ELD HoS audit and correction guidance application (109)and/or the commercial vehicle-specific ELD HoS audit and correctionguidance application (103) are also configured to provide intelligentvoice guidance through log entry auditing and editing procedures inmultiple languages.

Furthermore, the in-vehicle ELD HoS audit and correction guidanceapplication (109) and/or the commercial vehicle-specific ELD HoS auditand correction guidance application (103) are also capable of generatingurgent regulatory violation alerts and/or upcoming deadlines for aregulatory violation trigger point as a pre-violation alert. Eachviolation or pre-violation alert may be generated in form of an alertsiren, a voice message, a textual message, and/or another aural orvisual indicator. In addition, the commercial fleet-level multiplevehicle ELD HoS audit and correction management application (113) andthe commercial fleet-level multiple vehicle ELD log and databasemanagement system (105) are also configured to monitor and determinechronically-inaccurate commercial vehicle drivers and/or commercialvehicles that cause repeated and inaccurate driver log entries. Forexample, if a particular commercial vehicle driver makes repeatedmistakes of not logging into the vehicle ELD (121) before an on-dutydriving, or not logging out of the vehicle ELD (121) after the on-dutydriving is completed, the commercial fleet-level multiple vehicle ELDHoS audit and correction management application (113) and the commercialfleet-level multiple vehicle ELD log and database management system(105) may identify the particular commercial vehicle driver as a“chronically-inaccurate repeat offender,” and alert the commercialvehicle operations quality controller to prevent or reduce similarmistakes by the particular commercial vehicle driver in the future. Suchproactive and intelligent regulatory violation quality control protocolsenhance the utility of the commercial fleet-level ELD HoS audit andcorrection guidance system to minimize costly regulatory penalties,improve regulatory compliance among employees, and optimize commercialvehicle operations.

In the preferred embodiment of the invention, the in-vehicle ELD HoSaudit and correction guidance application (109), the commercialvehicle-specific ELD HoS audit and correction guidance application(103), and/or the commercial fleet-level multiple vehicle ELD HoS auditand correction management application (113) are configured to generateinteractive and dynamic voice guidance to assist a commercial vehicledriver or a commercial vehicle operations quality controller to edit oramend inadvertent errors and to confirm desired changes to a commercialvehicle electronic driver log before a legally-mandated log correctionperiod expires. Moreover, the interactive and dynamic voice guidance forELD HoS audit and correction is typically not merely a pre-recordedstatic voice narration, but rather an intelligent artificialintelligence-based voice guidance that corresponds to real-time changesto the commercial vehicle electronic driver log, as streams of incomingOBD, ECU, and/or ELD data parameters continue to update the commercialvehicle electronic driver log, if the log is currently still in anactive-synthesis mode. Preferably, the interactive and dynamic voiceguidance for ELD HoS audit and correction is offered in multiplelanguages (i.e. English, Spanish, Chinese, etc.) to enable a preferrednative language selection that the commercial vehicle driver or thecommercial vehicle operations quality controller is most familiar with.

In the preferred embodiment of the invention, the interactive voiceguidance provided by a plurality of ELD HoS audit and correctionguidance or management applications (e.g. 103, 109, 113) empowersdrivers and operations controllers to immerse intelligent and dynamicdata-incorporating voice guidance and related voice command ortouch-screen menu interactions in their native languages, such asEnglish, Spanish, Chinese, and Hindi. The multi-language voice guidancecapabilities of the ELD HoS audit and correction guidance system furtherenhances inadvertent log error correction rates and regulatorycompliance rates for commercial vehicle drivers and fleet operationsquality controllers, regardless of their native languages and culturalbackgrounds.

Furthermore, in one embodiment of the invention, the vehicle ELD (121)is capable of tracking each driver's activity status. For example, ifthe automotive vehicle has a nonzero speed for a particular amount oftime while its engine is running, the driver's driving activity statusis analyzed, determined, and recorded by the vehicle ELD (121) as beingengaged in an “on-duty” status. The vehicle ELD (121) is capable ofobjectively determining and confirming the driver's “on-duty” or activedriving status by analyzing the incoming machine-generatedvehicle-related output parameters from the vehicle OBD device (119) inreal time. Furthermore, in some embodiments, “on-duty” or “off-duty”statuses may also be determined at least in part by a driver's log-inand log-off actions via a user interface associated with the vehicle ELD(121), as each driver initiates or ends a commercial driving activityfor a particular workday. Each driver may access and modify log-in orlog-off events via the in-vehicle display connected to ELD (107), theportable electronic device for the commercial vehicle driver (101), oranother electronic device configured to execute a user interfaceapplication for the vehicle ELD (121).

In various embodiments of the invention, the record generated and storedby the vehicle ELD (121) becomes an electronic driver activity log (e.g.active, inactive, resting, sleeping, etc.) correlated to a system timeclock, and in some instances, become part of a driver's vehicleinspection report (DVIR). Moreover, in the preferred embodiment, thevehicle ELD (121) also enables the driver to manually enter or describehis or her driving status (e.g. active, inactive, resting, sleeping,etc.) correlated to the system time clock. Preferably, the vehicle ELD(121) accepts the driver's manual data entry to compare against and/ormerge with machine-determined driver's activity log information derivedfrom the vehicle OBD device (119), and completes synthesis of theelectronically-generated driver activity log that incorporates bothobjective (i.e. machine-determined) and subjective (i.e. driver-entered)information for enhanced details and accuracy.

In another example, if the automotive vehicle has a zero speed for acertain amount of time while its engine is idling, the associatedcommercial driver's driving activity status may be determined by thevehicle ELD (121) as still being engaged in an “on-duty” status, whichcounts toward the driver's on-the-job active hours, and not toward themandatory rest period. On the other hand, if the vehicle's engine itselfis turned off for a certain amount of time, the associated driver'sdriving activity status may be determined by the vehicle ELD (121) asbeing “off-duty,” inactive, and/or restful from work, and recorded bythe vehicle ELD (121) as part of the mandatory rest period. In thepreferred embodiment of the invention, the vehicle ELD (121) isconfigured to associate and/or record timestamps generated by a systemclock with durations and changes in each driving activity status, whichalso become part of the electronically-generated driving activity logsfor a plurality of drivers that time-share the automotive vehicle.

Furthermore, the vehicle ELD (121), as shown in FIG. 1, is a specializeddriver activity log-generating electronic device connected to thevehicle OBD device (119). In the preferred embodiment, the vehicle ELD(121) is a discrete piece of hardware device operatively connected tothe vehicle OBD device (119) via a physical cable or a wirelesscommunication protocol. In another embodiment, the vehicle ELD (121) isan integrated device that incorporates the vehicle OBD device (119)within its physical casing.

In the preferred embodiment of the invention, the vehicle ELD (121) isconfigured to analyze real-time OBD output data parameters toobjectively derive or confirm an ongoing driver activity. For example,the vehicle ELD (121) can measure and objectively confirm a commercialvehicle driver's on-duty driving by tracking a nonzero vehicle speeddata parameter and an engine “on” status signal from the vehicle OBDdevice, until the commercial vehicle driver stops and turns off theengine.

Similarly, the vehicle ELD (121) can objectively measure and confirm thecommercial vehicle driver's off-duty resting period with a system clockand a duration of the engine “off” status signal. In some cases, thevehicle ELD (121), either singularly or in combination with thecommercial fleet-level multiple vehicle ELD log and database managementsystem (105) and the portable or stationary electronic device forvehicle fleet monitoring station (111), is also configured to analyzethe real-time OBD output data parameters and manual entries by a driverto detect anomalous or unusual data elements that are likely to beinadvertent erroneous entries form the vehicle OBD device (119) or thedriver. Once likely-inadvertent and likely-erroneous entries areidentified by the system, at least one of the in-vehicle ELD HoS auditand correction guidance application (109), the commercialvehicle-specific ELD HoS audit and correction guidance application(103), and/or the commercial fleet-level multiple vehicle ELD HoS auditand correction management application (113) is configured to generate apre-violation alert or a siren as part of a machine-generated dynamicvoice guidance. The machine-generated dynamic voice guidance is furthersynchronized with a driver auditing-mode graphical user interface andother log entry amendment-enabling menus to prevent a regulatoryviolation before an actual violation related to commercial vehicledrivers' resting requirements, speed limit requirements, substitutedriver requirements, vehicle maintenance reporting requirements, and/orother regulatory issues is triggered.

Importantly, “pre-violation” alerts generated by various embodiments ofthe present invention can prevent unnecessary fines or penalties arisingfrom commercial vehicle drivers' accidental or intentional violations offederal, state, and/or municipal regulatory requirements. Themachine-generated dynamic voice guidance that incorporates the“pre-violation” alert may utilize real-time data output parameters fromthe in-vehicle sensors and ECU (117), the vehicle OBD device (119), thevehicle ELD (121), or cloud-based historical vehicle performance ordriver behavioral data accessed from the commercial fleet-level multiplevehicle ELD log and database management system (105). Furthermore,regulatory compliance related to a required duration of the commercialvehicle driver's rest can also be tracked and alerted to appropriateauthorities (e.g. local, national, and/or federal traffic safetyenforcement agencies, fleet managers, etc.) by the vehicle ELD (121)connected to the in-vehicle ELD and OBD data transceiver unit (123). Thein-vehicle ELD and OBD data transceiver unit (123) is configured tocommunicate wirelessly with portable electronic devices and/or computerservers via a cellular network, a satellite network, a wireless LAN,another wireless data network, or a combination thereof, wherein theportable electronic devices and/or the computer servers are operated bya remote monitoring station overseeing the commercial fleet-levelmultiple vehicle ELD log and database management system (105) and aplurality of drivers, operations quality controllers, and regulatoryauthorities, as shown in FIG. 1.

Continuing with the preferred embodiment of the invention as shown inFIG. 1, each of the portable electronic devices (i.e. 101, 111) forcommercial vehicle drivers and operations quality controllers is a smartphone, a tablet computer, a laptop computer, a desktop computer, aspecialized proprietary commercial fleet management electronic device,or another portable electronic device, which is configured to executeone or more ELD HoS audit and correction guidance applications (i.e.103, 109, 113) in a CPU/APU (i.e. a central processing unit or anapplication processing unit) and a memory unit of each portableelectronic device. The portable electronic devices utilized by driversand vehicle operations quality controllers are operatively connected toeach other and other elements (e.g. 105, 115, etc.) of the ELD HoS auditand correction guidance system via the wired and/or wireless datanetwork (125), which may include a cellular network, a satellitenetwork, a wireless LAN, a cloud-computing resource network, or acombination thereof.

As shown by the embodiment of the invention illustrated in FIG. 1, thein-vehicle ELD HoS audit and correction guidance application (109), thecommercial vehicle-specific ELD HoS audit and correction guidanceapplication (103), the commercial fleet-level multiple vehicle ELD HoSaudit and correction management application (113), and the vehicle-sidesystem components (115) can communicate each other directly on apeer-to-peer basis in the wired and/or wireless data network (125).Alternatively, electronic communications and data transfer among theseelements can be mediated, managed, or controlled by the commercialfleet-level multiple vehicle ELD log and database management system(105), which is typically executed and hosted by one or more computerservers in a remote monitoring station. For example, the commercialfleet-level multiple vehicle ELD log and database management system(105) may have data correction or overriding privileges to amenderroneous ELD log and DVIR entries before or after the data lockoutperiod for recent ELD log entries and DVIR entries, depending onfederal, state, municipal, and/or corporate regulatory compliance rulesfor the data lockout. In another example, the commercial fleet-levelmultiple vehicle ELD log and database management system (105) mayintervene, overtake, or correct communication disruptions or noresponses among a plurality of ELD HoS audit and correction guidance ormanagement applications (103, 109, 113) and vehicle-side systemcomponents (115), if a particular commercial vehicle driver or anotherrelated participant fails to respond to the system's repeated alerts forELD log pre-violations or data abnormalities that require log entryamendments or corrections.

It should be noted that federal, state, municipal, and/or corporateregulations may require each commercial vehicle driver to finalize hisor her on-duty ELD log and DVIR entries within a defined time limit(e.g. within 24 hours of on-duty vehicle operation, etc.) beforefreezing and locking the contents of the ELD and DVIR logs fromadditional modifications to preserve the data integrity fromunauthorized or undesirable retroactive alterations. Therefore, the ELDHoS audit and correction guidance system improves timely corrections oramendments to inadvertent ELD log entry errors before triggeringregulatory violations by proactively identifying, encouraging, andaccommodating log entry corrections before the data log freeze period isreached.

FIG. 2 shows a driver auditing-mode screenshot (200) from an ELD HoSaudit and correction guidance system, in accordance with an embodimentof the invention. In a preferred embodiment of the invention, anin-vehicle ELD HoS audit and correction guidance application (e.g. 109in FIG. 1), a commercial vehicle-specific ELD HoS audit and correctionguidance application (e.g. 103 in FIG. 1), or a commercial fleet-levelmultiple vehicle ELD HoS audit and correction management application(e.g. 113 in FIG. 1) is configured to generate a driver auditing modeuser interface on an in-vehicle display connected to ELD (e.g. 107) oron a portable electronic device utilized by a commercial vehicle driver(e.g. 101).

In the preferred embodiment of the invention, the ELD HoS audit andcorrection guidance system is configured to determine that acurrently-active commercial vehicle electronic driver log contains apre-violation item or an anomalous log element that urgently requiresthe commercial vehicle driver's immediate attention for timely amendmentto avoid triggering a regulatory violation. Preferably, the ELD HoSaudit and correction guidance system is able to determine and identifythe pre-violation item or the anomalous log element at least severalhours before a mandatory data content freeze period is reached for thecurrently-active commercial vehicle electronic driver log to givesufficient time to the commercial vehicle driver to correct or amend thepre-violation item or the anomalous log element, if it is a correctableand inadvertent error.

In the example shown as the driver auditing-mode screenshot (200) inFIG. 2, the driver auditing mode user interface displays a log timelinewith a highlighted or a blacked-out section (e.g. midnight (M)˜11:07 AM)that the ELD HoS audit and correction guidance system identified as apotentially-inadvertent error caused by the commercial vehicle driver.The driver auditing mode user interface also produces achronologically-organized list of ELD log activities, including thelikely-erroneous “on-duty” entry (e.g. “ON” (midnight (M)˜11:07 AM)),active driving entries (e.g. “DRV’ (11:07 AM˜11:09 AM), (3:26 PM˜3:44PM)), and off-duty entries (e.g. “OFF” (3:44 PM˜ongoing)). In thisexample, a break rule violation was triggered at 11:07 AM, while a shiftrule violation was triggered at 3:26 PM. The shift rule violation inthis case may be a second-order effect of the break rule violation thatwas accidentally triggered due to the incorrect log entry of an“on-duty” status between midnight (M) and 11:07 AM.

Importantly, in this example, the ELD HoS audit and correction guidancesystem can make a preliminary determination of anomalous data in thisexample by intelligently recognizing that an “on-duty” status durationof 11 hours and 7 minutes, during which the vehicle did not engage inany active driving, is indicative of a mistakenly-forgotten log-outconfirmation by the commercial vehicle driver at midnight (M). If thecommercial vehicle driver simply forgot to log out of the vehicle ELD atthe end of his or her work period, the “on-duty” status may accidentallyremain turned on while the commercial vehicle electronic driver log isstill in a recording mode. If left uncorrected, the “on-duty” statusthat remained active for more than 11 hours (i.e. without any drivingactivity between midnight (M)˜11:07 am) triggers a mandatory rest periodviolation after a certain number of “on-duty” log hours elapses.

FIG. 3 shows a subsequent screenshot (300) of the driver auditing modefrom the ELD HoS audit and correction guidance system in a sequenceafter the driver auditing-mode screenshot (200), in accordance with anembodiment of the invention. In a preferred embodiment of the invention,the driver auditing mode user interface presented on the in-vehicledisplay (e.g. 107) or on the portable electronic device (e.g. 101) isgenerated by the in-vehicle ELD HoS audit and correction guidanceapplication (e.g. 109 in FIG. 1), the commercial vehicle-specific ELDHoS audit and correction guidance application (e.g. 103 in FIG. 1), orthe commercial fleet-level multiple vehicle ELD HoS audit and correctionmanagement application (e.g. 113 in FIG. 1).

As shown in the current screenshot (300) of the driver auditing modefrom the ELD HoS audit and correction guidance system in FIG. 3, theauditing mode invokes an edit feature that draws a frame around thehighlighted or the blacked-out section (e.g. midnight (M)˜11:07 AM),which the ELD HoS audit and correction guidance system identified as thepotentially-inadvertent error caused by the commercial vehicle driver inFIG. 2. The commercial vehicle driver or another user is then able tomodify or amend erroneous information, if the log entries are corrigiblemistakes. In one embodiment of the invention, human entry errors, suchas forgetting to log in or log out of the vehicle ELD interface, may beconsidered corrigible mistakes that can utilize the driver auditing modefor log entry amendments, while machine entry errors, such asincorporating ECU parameters that indicate whether the vehicle enginewas on or off, or whether the vehicle was driving forward or not, may beconsidered objective and thus “incorrigible” log entries.

FIG. 4 shows a driver status log edit screenshot (400) from an ELD HoSaudit and correction guidance system, in accordance with an embodimentof the invention. The driver status log edit screenshot (400) is asubsequent sequence following the driver auditing mode from the ELD HoSaudit and correction guidance system, wherein the commercial vehicledriver or another user is able to modify the erroneous “on-duty” logentry to an “off-duty” log entry or to a “sleeper berth” rest log entryfor a time section that was previously identified as potentiallyerroneous (e.g. midnight (M)˜11:07 AM) by the ELD HoS audit andcorrection guidance system.

As shown in FIG. 4, the commercial vehicle driver or another authorizeduser is able to amend a potentially-erroneous log entry after a systemalert or a siren generated by the ELD HoS audit and correction guidancesystem. The system alert may be textual, graphical, aural,machine-generated phone calls, or any combination thereof, which promptsthe commercial vehicle driver or another relevant user to interact withthe driver auditing mode user interface to correct or amend urgent andcorrigible mistakes in the ELD log.

In a preferred embodiment of the invention, the driver auditing modeuser interface and the edit status log interface are presented on thein-vehicle display (e.g. 107) or on the portable electronic device (e.g.101), and are generated by the in-vehicle ELD HoS audit and correctionguidance application (e.g. 109 in FIG. 1), the commercialvehicle-specific ELD HoS audit and correction guidance application (e.g.103 in FIG. 1), or the commercial fleet-level multiple vehicle ELD HoSaudit and correction management application (e.g. 113 in FIG. 1), aspreviously described in conjunction with FIGS. 1˜3.

FIG. 5 shows a driver auditing-mode screenshot (500) afterdriver-initiated corrections from an ELD HoS audit and correctionguidance system, in accordance with an embodiment of the invention. Thedriver auditing-mode screenshot (500) as shown in FIG. 5 is a subsequentsequence following the completion of manual log entry amendments orcorrections by the commercial vehicle driver or another responsibleentity, such as a commercial vehicle operations quality controller or afleet vehicle manager.

As shown by the driver auditing-mode screenshot (500), the ELD HoS auditand correction guidance system has completed assisting the commercialvehicle driver or another responsible party to correct the inadvertentlog entry error, and the break violation and the shift violation warningindicators have both been removed from the driver auditing-modeinterface. The erroneous “on-duty” status between midnight (M) and 11:07AM is now corrected to an “off-duty” status, as shown in FIG. 5. Thiscorrection prevents triggering of accidental and unintended regulatoryviolations for not taking mandatory rest between on-duty statuses forthe commercial vehicle driver.

In a preferred embodiment of the invention, the driver auditing modeuser interface and the edit status log interface are presented on thein-vehicle display (e.g. 107) or on the portable electronic device (e.g.101), and are generated by the in-vehicle ELD HoS audit and correctionguidance application (e.g. 109 in FIG. 1), the commercialvehicle-specific ELD HoS audit and correction guidance application (e.g.103 in FIG. 1), or the commercial fleet-level multiple vehicle ELD HoSaudit and correction management application (e.g. 113 in FIG. 1), aspreviously described in conjunction with FIGS. 1˜4.

FIG. 6 shows a vehicle and driver selection interface screenshot (600)from an ELD HoS audit and correction guidance system, in accordance withan embodiment of the invention. The vehicle and driver selectioninterface, as exemplified in FIG. 6, enables a commercial vehicleoperations quality controller or a commercial vehicle driver to assignor release a particular commercial vehicle for ELD log or DVIRgeneration for a main driver, or a co-driver who may be time-sharingwork hours with the main driver in the particular commercial vehicle.Furthermore, the vehicle and driver selection interface also enables thecommercial vehicle operations quality controller or the commercialvehicle driver to open or close ELD logs or driver vehicle inspectionreports (DVIRs) for timely corrections or amendments before the log datacontents are legally required to be frozen from any additional changesfor regulatory compliance imposed on commercial vehicle fleetoperations.

FIG. 7 shows a commercial driver electronic logging current status menuscreenshot (700) from an ELD HoS audit and correction guidance system,in accordance with an embodiment of the invention. In a preferredembodiment of the invention, an in-vehicle ELD HoS audit and correctionguidance application (e.g. 109 in FIG. 1), a commercial vehicle-specificELD HoS audit and correction guidance application (e.g. 103 in FIG. 1),or a commercial fleet-level multiple vehicle ELD HoS audit andcorrection management application (e.g. 113 in FIG. 1) is configured togenerate a commercial driver electronic logging current status menu onan in-vehicle display connected to ELD (e.g. 107) or on a portableelectronic device utilized by a commercial vehicle driver (e.g. 101).

In the preferred embodiment of the invention, the ELD HoS audit andcorrection guidance system is capable of determining an upcomingregulatory violation deadline for the commercial vehicle driver, who iscurrently operating the vehicle while the driver-specific ELD log isbeing generated in real time. As shown by the commercial driverelectronic logging current status menu screenshot (700), the main driveris currently on duty and has an upcoming rest or shift violation inapproximately two hours (i.e. 1 PM) from present time (i.e. 11 AM).Preferably, the upcoming rest or shift violation is graphicallyindicated as a colored or highlighted vertical bar at the time of aviolation trigger point (i.e. 1 PM) in the near-future timeline, whichis located on the right side of the present time reference (i.e. 11 AM),as shown in FIG. 7.

The graphical indication of the upcoming regulatory violation deadlineintuitively and preemptively reminds the commercial vehicle driver or afleet operations quality controller that an action (i.e. taking a rest,shifting duty with another driver, performing a legally-required vehiclemaintenance task, etc.) needs to be taken in the near future. Thispreemptive reminder feature of the ELD HoS audit and correction guidancesystem further reduces unnecessary and undesirable regulatory violationnotices for commercial vehicle fleet operations that may face sanctionsand/or hefty penalties, if legally-mandated regulatory rules forcommercial vehicle operations are violated inadvertently by one or moredrivers, contractors, or other employees.

FIG. 8 shows a system block diagram example (800) for a vehicleelectronic logging device (ELD), which is a component in a commercialfleet-level ELD HoS audit and correction guidance system, in accordancewith an embodiment of the invention. In this system block diagramexample (800), the vehicle ELD (e.g. 121 of FIG. 1) includes a CPU(801), a memory unit (811), a data storage unit (809), a display driverand/or LED control unit (803), an ELD log audit and correction module(807), an input/output interfaces (813), and a power supply (837).Optionally, the vehicle ELD also has a global positioning system (GPS)receiver (805).

In one embodiment of the invention, these hardware system blocks (e.g.800) for the vehicle ELD are configured to execute the ELD log audit andcorrection module (807) in the CPU (801) and the memory unit (811),wherein the ELD log audit and correction module (807) contains aplurality of logical blocks, as exemplified by FIG. 9. In anotherembodiment of the invention, the ELD log audit and correction module(807) may be hard-coded into a semiconductor chip as a hardwarecomponent within the hardware system blocks of the vehicle ELD (e.g. 121in FIG. 1). Furthermore, the vehicle ELD may also incorporate a wirelesstransceiver for ELD and OBD data communication with a plurality ofportable electronic devices and a commercial fleet vehicle maintenanceand ELD database management system via a wireless data network.Alternatively, the vehicle ELD may be operatively connected to aseparate wireless transceiver unit for ELD and OBD data communicationwith various components of the commercial fleet-level ELD HoS audit andcorrection guidance system. The wireless transceiver may be configuredto transmit or receive data packets via a cellular network, a satellitenetwork, a land-mobile radio network, or via another wirelesscommunication method.

Continuing with FIG. 8, the data storage unit (809) in the vehicle ELDcan store OBD data streams from a vehicle OBD device and any informationentered by a time-sharing vehicle driver or a commercial fleet operationpersonnel. Furthermore, the ELD log audit and correction module (807)executed in the vehicle ELD can retrieve the OBD data streams,environmental sensor readings associated with the time-shared vehicle,and other driver activity-related information to calculate and/ordetermine current status of a vehicle repair/maintenance need or aspecific driver activity (e.g. actively driving, passively idling,resting, signing off from an on-duty status, etc.). For example, vehiclespeed, acceleration, engine on/off status, driver position/locationsensing within the time-shared vehicle (e.g. driver's seat, passengerseat, sleeper cabin, outside the vehicle, etc.), and other vehicle OBDand sensor output parameters can be utilized by the ELD log audit andcorrection module (807) to determine the current status of specificdriver activities, from which one or more pre-violation or violationalerts and voice and/or visual audit-mode and log content correctionguidance can be generated to encourage timely amendments topotentially-erroneous vehicle ELD log entries.

In some embodiments of the invention, the vehicle OBD and sensor outputparameters may also be utilized to detect a potential damage orendangerment to a fragile cargo item, excessively cold or hottemperatures inside the time-shared vehicle, extreme humidity or drynessin the time-shared vehicle's cargo space, or excessive fuel consumptionby a particular driver. Any of these detected information during aparticular driver's operating hours may be synthesized and recorded aspart of the driver-specific ELD log, if desired by the commercial fleetoperation personnel or government regulators.

In some instances, the vehicle ELD may integrate or connect to locationtracking unit(s), such as the GPS receiver (805) in FIG. 8. An abruptoutage or improper GPS coordinate readings for the time-shared vehiclefrom the GPS receiver (805) or another location tracking unit mayindicate a potential endangerment to the currently logged-in driver,which can be detected and alerted to the commercial fleet operationpersonnel or the government regulators via a wireless data network. TheELD log audit and correction module (807) can be configured to generatetextual, aural, or multimedia alerts to the currently logged-in driver,the commercial fleet operation personnel, and/or the governmentregulators, based on alerts determined by the vehicle ELD.

Furthermore, the vehicle ELD may also generate alerts or indicatemonitoring statuses via a plurality of LED indicator lights connected tothe display driver and/or LED control unit (803) and a display driveroutput (835). Moreover, various hardware components (i.e. 801, 803, 805,807, 809, 811, 813, 837) of the vehicle ELD can transmit and receivedata among each other via an internal bus (839) and various electricalconnections (815, 817, 819, 821, 823, 825).

In the embodiment of the invention as shown in FIG. 8, the vehicle ELDalso includes the power supply unit (837), which supplies electricalpower to various hardware components (i.e. 801, 803, 805, 807, 809, 811,813, 837) in the hardware system blocks of the vehicle ELD. Furthermore,the vehicle ELD may also include the input/output interfaces (813) thatcan accommodate data communication for I/O ports (827), smart cardreaders (829), network connections (831), and an audio out connection(833) to a speaker. As shown in the system block diagram example (800),in this embodiment of the invention, the input/output interfaces (813)are operatively connected to the internal bus (839), which cancommunicate with any other components in the vehicle ELD.

FIG. 9 shows an example (900) of an ELD log audit and correction module(901) in an ELD HoS audit and correction guidance system, in accordancewith an embodiment of the invention. In a preferred embodiment of theinvention, the ELD log audit and correction module (901) corresponds toelement 807 in FIG. 8. The ELD log audit and correction module (901) istypically integrated into a vehicle electronic logging device (ELD),which is typically a vehicle-installed specialized hardware device thatconnects to a vehicle OBD device and an ELD/OBD data transceiver unit,as previously shown in FIG. 1.

In a preferred embodiment of the invention, the ELD log audit andcorrection module (901) comprises a driver-specific OBD informationmanagement module (903) for recording and categorizing a vehicle'sspeed, acceleration, mileage, engine activity, OBD fault codes, andvehicle repair/maintenance-related output parameters per driver. An OBDdata stream which contains vehicular dynamics, engine on/off statuses,OBD fault codes (if any), and fuel consumption information can bestored, categorized, and extracted in the driver-specific OBDinformation management module (903).

The ELD log audit and correction module (901) also includes a driverauthentication and vehicle access duration tracking module (905). Thismodule is configured to authenticate a particular driver operating atime-shared vehicle among a plurality of registered drivers in thevehicle ELD, and is also configured to track and record the particulardriver's vehicle access duration and any vehicle OBD fault codes ormaintenance needs. The particular driver's vehicle access duration maybe inferred by the driver authentication timing with the vehicle ELD,speedometer readings, and engine on/off statuses that suggest theparticular driver's on-duty driving activities or resting periods.Furthermore, the particular driver's vehicle access duration can be mademore precise by manual or machine-based automated entry of theparticular driver's expected operating hours in the time-shared vehicle.

Furthermore, the ELD log audit and correction module (901) alsoincorporates a driver-specific resting activity tracking module (907),which is configured to determine, track, and record a driver's restingperiods based on machine-generated vehicle data parameters, such asmotion sensor values in the sleeper cabin, driver authentication timingwith the vehicle ELD, speedometer readings, engine on/off statuses, anddriver operation schedule entries. In addition, the driver's restingperiods can be tracked more accurately if the driver's expected restingschedules are uploaded to the driver-specific resting activity trackingmodule (907).

Continuing with FIG. 9, the ELD log audit and correction module (901)also incorporates a driver-specific ELD log-in, log-out, and DVIRreporting module (909), which is capable of initiating (i.e. “loggingin”), terminating (i.e. “logging out” or signing off), and/ortransferring (i e “handover”) a driver-specific ELD or DVIR loggeneration privileges in the vehicle ELD. A plurality of drivers whotime-share a vehicle can utilize one or more portable electronic devicesand corresponding remote ELD/DVIR log handover mobile applications torequest, grant, or deny a driver-specific ELD/DVIR log handover for thevehicle ELD installed in the time-shared vehicle, even when a particulardriver has forgotten to log out of the vehicle ELD after his or herallotted driving operation period and is no longer near the time-sharedvehicle.

Moreover, the ELD log audit and correction module (901) alsoincorporates a federal, state, or municipal commercial ELD regulationpre-violation and violation real-time detection module (913) thatcompares the most up-to-date regulatory violation rules from variouslocal, state, and national governments against recent log entries into avehicle ELD log. If there is an existing or upcoming violation of aregulatory requirement based on the past or the current trends andentries in the vehicle ELD log, the federal, state, or municipalcommercial ELD regulation pre-violation and violation real-timedetection module (913) generates a violation or pre-violation alert inform of visual, aural, textual, email, or a combination thereof toprompt a driver or a fleet operations controller to perform timelycorrection to the vehicle ELD log before the data contents are frozen(e.g. 24 hours after each entry in the vehicle ELD log, etc.) fromadditional amendments due to regulatory vehicle log lock-uprequirements.

Furthermore, the ELD log audit and correction module (901) also containsan ELD HoS audit and correction guidance module (915) configured togenerate and manage various driver auditing-mode interfaces (e.g. 919)and vehicle operations quality controller auditing-mode or editing-modeinterfaces, wherein each interface graphically and/or aurally guidessystem users on a step-by-step basis for intuitive and convenientusability. The ELD HoS audit and correction guidance module (915) alsooperates in conjunction with an ELD HoS audit and correction voiceguidance module (917) to provide a dynamically-adaptive voice guidanceassistance to the system user for each step required in vehicle logentry amendment or correction procedures. In some cases, thedynamically-adaptive voice guidance assistance improves log entrycorrection response time and compliance rates by proactively andverbally encouraging log entry corrections before a regulatory violationis triggered.

In addition, the ELD log audit and correction module (901) also includesan information display management module (911). The information displaymanagement module (911) is configured to display, highlight, and modifyELD log timelines, ELD log entries, violation alerts, driving activitystatuses, and other information pertinent to the ELD HoS audit andcorrection guidance system. Furthermore, these graphical and textualinformation associated with the vehicle ELD can also be displayed by thecommercial fleet-level multiple vehicle ELD log and database managementsystem.

In one embodiment of the invention, various modules (903, 905, 907, 909,911, 913, 915, 917, 918) contained inside the ELD log audit andcorrection module (901) may be software elements that are executed in aCPU/APU or a memory unit of a hardware device, such as system blockcomponents (e.g. 800 of FIG. 8) of a vehicle electronic logging device(ELD). In another embodiment of the invention, the ELD log audit andcorrection module (901) may be a combination of software elements andhardware elements that conceptually constitute various components (903,905, 907, 909, 911, 913, 915, 918) of the ELD log audit and correctionmodule (901). Yet in another embodiment of the invention, the ELD logaudit and correction module (901) may be entirely implemented into asemiconductor chip, which makes the ELD log audit and correction module(901) a system-on-chip (SoC) hardware solution.

FIG. 10 shows an example of a portable electronic device (1000)incorporating a commercial vehicle-specific ELD HoS audit and correctionguidance application module (1017), in accordance with an embodiment ofthe invention. The commercial vehicle-specific ELD HoS audit andcorrection guidance application module (1017) contains at least one of acommercial vehicle-specific ELD HoS audit and correction application, anin-vehicle ELD HoS audit and correction guidance application, and acommercial fleet-level multiple vehicle ELD HoS audit and correctionmanagement application, each of which is configured to guide or managecorrective steps in reducing inadvertent errors in ELD driver logs.

In a preferred embodiment of the invention, the portable electronicdevice may be a smart phone, a tablet computer, a notebook computer, apersonal computer, a special-purpose proprietary ELD data controllerdevice, or another transportable electronic device that can execute avehicle ELD rule compliance and inspection voice assistant applicationin a CPU, an APU, and/or a memory unit of the portable electronicdevice. The commercial vehicle-specific ELD HoS audit and correctionguidance application module (1017) may comprise software elements (e.g.a vehicle ELD rule compliance and inspection voice assistant mobile app)stored in a non-volatile data storage, or embedded software elementshard-coded and incorporated in a semiconductor chip as a piece ofhardware. The portable electronic device is configured to providevehicle ELD rule compliance and inspection voice assistant userinterfaces for creating, modifying, authorizing, and sharing vehicle ELDlog files, and may also function as a multi-purpose electroniccommunication device that provides Internet web browsing, textmessaging, email communication, and voice call capabilities.

As shown in the system block diagram example (1000) of FIG. 10, theportable electronic device has a CPU or an APU (1001), which isoperatively connected to a memory unit (1013), a local data storage(1005), a camera processing unit (1003), a graphics unit (1007) (e.g. agraphics processor, a display driver, and etc.), a power management unit(1009), a peripheral device and/or external communication I/O interface(1011), a digital signal processing (DSP) unit for cloud server access(1015), the commercial vehicle-specific ELD HoS audit and correctionguidance application module (1017), and a sound unit. These logicalunits may be placed on a single printed circuit board (1025) in oneembodiment of the invention, or a plurality of printed circuit boards inanother embodiment of the invention.

In the preferred embodiment of the invention, the CPU/APU (1001) isconfigured to control each logical unit operatively (i.e. directly orindirectly) connected to the CPU/APU (1001). The memory unit (1013)typically comprises volatile memory banks based on DRAM's. In someembodiments of the invention, the memory unit (1013) may usenon-volatile memory technologies such as SRAM's and/or Flash memory. Thememory unit (1013) is capable of storing programs and applications whichcan be executed by the CPU/APU (1001), the graphics unit (1007), oranother logical unit operatively connected to the memory unit (1013).

In particular, in the preferred embodiment of the invention,instructions, datasets, and codes originating from the commercialvehicle-specific ELD HoS audit and correction guidance applicationmodule (1017) can be executed on the CPU/APU (1001) and the memory unit(1013) of the portable electronic device to provide ELD HoS audit andcorrection guidance mobile applications. The commercial vehicle-specificELD HoS audit and correction guidance application module (1017) may be aseparate standalone logical unit, as shown in FIG. 10, or a collectionof software or machine codes associated with the commercialvehicle-specific ELD HoS audit and correction guidance application inthe local data storage (1005). Preferably, the commercialvehicle-specific ELD HoS audit and correction guidance applicationmodule (1017) contains one or more logical units (e.g. 903, 905, 907,909, 911, 913, 915, 917, 919) previously described in FIG. 9.

Continuing with FIG. 10, any software and programs executed on theCPU/APU (1001) and the memory unit (1013) of the portable electronicdevice may be part of an operating system, or a separate applicationinstalled on the operating system of the portable electronic device.Furthermore, the camera processing unit (1003) is operatively connectedto a camera lens on the portable electronic device, and is able toprocess image-related data from the camera lens in association with theCPU/APU (1001) and/or other logical units in the portable electronicdevice to produce live recorded video information, which may be storedin the local data storage (1005). In addition, a microphone operativelyconnected to the sound unit can produce live recorded audio information,which can also be stored in the local data storage (1005).

Moreover, as shown in FIG. 10, the digital signal processing (DSP) unitfor cloud server access (1015) is operatively connected to an radiofrequency (RF) antenna. The DSP unit for cloud server access (1015) isgenerally configured to receive and transmit radio data and/or voicesignals wirelessly for a desktop computer, a laptop, a mobilecommunication device, an electronic goggle, or another suitableelectronic system. In addition, the power management unit (1009) isoperatively connected to a power supply unit and a power source (e.g.battery, power adapter) (1021), and the power management unit (1009)generally controls power supplied to the portable electronic device andits logical units. Moreover, the peripheral device and/or externalcommunication I/O interface (1011) as shown in FIG. 10 can beoperatively connected to one or more peripheral devices, wirelessdevices, USB ports, and other external data communication media (1023).

Continuing with FIG. 10, in the preferred embodiment of the invention,the graphics unit (1007) in the system block diagram example (1000) forthe portable electronic device comprises a graphics processor, a displaydriver, a dedicated graphics memory unit, and/or anothergraphics-related logical components. In general, the graphics unit(1007) is able to process and communicate graphics-related data with theCPU/APU (1001), the display driver, and/or the dedicated graphics memoryunit. The graphics unit (1007) is also operatively connected to one ormore display units (1019). In addition, the CPU/APU (1001) may beoperatively connected to the sound unit which contains audio-relatedlogical components for generation or recording of audio data from amicrophone operatively connected to the portable electronic device.

Various embodiments of the present invention provide several keyadvantages over conventional methods of regulatory compliance incommercial vehicle operations. One advantage of an embodiment of thepresent invention is providing a novel commercial fleet-level ELD logaudit and correction guidance system that proactively identifiespotentially-erroneous or incorrect driver activity log entries in realtime and reduces regulatory violations by encouraging timely correctionsof erroneous log entries via an intuitive log entry audit and correctioninterface, multimedia alerts, and intelligent voice guidance tocommercial vehicle drivers and fleet operation managers.

Furthermore, another advantage of an embodiment of the present inventionis providing a dynamically-adaptable intelligent voice assistantincorporated into the novel commercial fleet-level ELD log audit andcorrection guidance system to generate proactive voice guidance throughlog entry audit and correction modes and user interfaces, which in turnimproves usability and correction response rates by commercial vehicledrivers and fleet operation managers.

In addition, another advantage of an embodiment of the present inventionis providing a novel commercial fleet-level ELD log audit and correctionguidance system that determines, warns, or reportschronically-inaccurate and “problematic” commercial vehicle drivers orcommercial vehicles that cause repeated and inaccurate driver logentries, which in turn minimizes regulatory penalties and optimizescommercial vehicle operational efficiencies.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

What is claimed is:
 1. A commercial fleet-level electronic loggingdevice (ELD) log audit and correction guidance system comprising: avehicle on-board diagnostics (OBD) device connected to an engine controlunit (ECU) or a vehicular control chip in a vehicle to record, diagnose,and generate an engine on or off status, vehicle speed data,acceleration and deceleration data, ambient air temperature data, andOBD fault codes as a raw OBD data stream; a vehicle electronic loggingdevice (ELD) connected to the vehicle OBD device, wherein the vehicleELD is configured to generate a driver-specific ELD log that contains acurrently logged-in driver's on-duty, off-duty, and resting activitiesassociated with the vehicle; an ELD and OBD data transceiver connectedto the vehicle ELD, wherein the ELD and OBD data transceiver isconfigured to transmit ELD and OBD data to components of the commercialfleet-level ELD log audit and correction guidance system that arelocated outside the vehicle; a commercial vehicle-specific ELD log auditand correction guidance application executed in a first portableelectronic device for the currently logged-in driver, wherein thecommercial vehicle-specific ELD log audit and correction guidanceapplication detects and identifies a potential error in thedriver-specific ELD log that contains the currently logged-in driver'son-duty, off-duty, and resting activities associated with the vehicle,and also creates a pre-violation alert triggered by an anomalous logelement that urgently requires the currently logged-in driver'simmediate attention for timely amendment to prevent a federal, state, ormunicipal violation notice related to a mandatory driver restrequirement, a substitute driver requirement, a speed limit requirement,a vehicle maintenance requirement, or another regulatory requirement forcommercial drivers, wherein the commercial vehicle-specific ELD logaudit and correction guidance application also generates a driverauditing-mode interface and an interactive voice guidance to prompt thecurrently logged-in driver to correct the potential error to avoid aregulatory violation; a commercial fleet-level multiple vehicle ELD logand database management system that analyzes, stores, and categorizes aplurality of driver-specific ELD logs for a plurality of drivers andvehicles in a commercial fleet operation; and a data communicationnetwork configured to provide a wireless data information transfer amongthe vehicle ELD, the ELD and OBD data transceiver, the first portableelectronic device, and the commercial fleet-level multiple vehicle ELDlog and database management system.
 2. The commercial fleet-levelelectronic logging device (ELD) log audit and correction guidance systemof claim 1, further comprising an in-vehicle ELD log audit andcorrection guidance application executed in an in-vehicle displayconnected to the vehicle ELD.
 3. The commercial fleet-level electroniclogging device (ELD) log audit and correction guidance system of claim1, further comprising a commercial fleet-level multiple vehicle ELD logaudit and correction management application executed in a portable orstationary electronic device for a vehicle fleet monitoring station. 4.The commercial fleet-level electronic logging device (ELD) log audit andcorrection guidance system of claim 1, further comprising a computerserver with a CPU and a memory unit that execute the commercialfleet-level multiple vehicle ELD log and database management system. 5.The commercial fleet-level electronic logging device (ELD) log audit andcorrection guidance system of claim 3, wherein at least one of thecommercial fleet-level multiple vehicle ELD log audit and correctionmanagement application and the commercial fleet-level multiple vehicleELD log and database management system is able to identify, alarm, orreport a commercial vehicle driver who repeatedly creates or enterserroneous data parameters into the driver-specific ELD log, which inturn triggers repeated regulatory violations.
 6. The commercialfleet-level electronic logging device (ELD) log audit and correctionguidance system of claim 1, further comprising in-vehicle sensors andthe engine control unit (ECU) that are operatively connected to thevehicle OBD device.
 7. The commercial fleet-level electronic loggingdevice (ELD) log audit and correction guidance system of claim 1,wherein the vehicle ELD comprises a CPU, a memory unit, an ELD log auditand correction module, a data storage unit, a power supply, and inputand output interfaces.
 8. The commercial fleet-level electronic loggingdevice (ELD) log audit and correction guidance system of claim 7,wherein the ELD log audit and correction module comprises adriver-specific OBD information management module for recording andcategorizing the vehicle's speed, acceleration, mileage, engineactivity, and vehicle maintenance needs per driver, a driverauthentication and vehicle access duration tracking module, adriver-specific resting activity tracking module, a driver-specific ELDlog-in, log-out, and DVIR reporting module, a federal, state, ormunicipal commercial ELD regulation pre-violation and violationreal-time detection module, an ELD log audit and correction guidancemodule, an ELD log audit and correction voice guidance module, an ELDlog audit and correction “auditing-mode” user interface, and aninformation display management module.
 9. The commercial fleet-levelelectronic logging device (ELD) log audit and correction guidance systemof claim 1, wherein the first portable electronic device is a smartphone, a tablet computer, a notebook computer, a personal computer, or aspecialized driving activity communication device.
 10. The commercialfleet-level electronic logging device (ELD) log audit and correctionguidance system of claim 1, wherein the vehicle is a truck, a van, abus, a taxi, a limousine, or a passenger vehicle, which is time-sharedamong the plurality of drivers.
 11. The commercial fleet-levelelectronic logging device (ELD) log audit and correction guidance systemof claim 1, wherein the data communication network is a cellularcommunication network, a satellite communication network, a land-mobileradio communication network, a wireless local area network, or acombination thereof.
 12. The commercial fleet-level electronic loggingdevice (ELD) log audit and correction guidance system of claim 3,wherein the commercial vehicle-specific ELD log audit and correctionguidance application, an in-vehicle ELD log audit and correctionguidance application, and the commercial fleet-level multiple vehicleELD log audit and correction management application are each configuredto process and recognize voice commands.